{"labelingInfo":null,"renderer":{"description":"Survey Data Locations","label":"Survey Point","symbol":{"angle":0,"color":[255,0,0,255],"outline":{"color":[255,255,0,255],"width":1},"size":8,"style":"esriSMSCircle","type":"esriSMS","xoffset":0,"yoffset":0},"type":"simple"},"transparency":0}
HasZ: false
HasM: false
Has Attachments: true
Has Geometry Properties: false
HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText
current_data_management_system (type: esriFieldTypeString, alias: Current Data Management System, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
date_range_of_records (type: esriFieldTypeString, alias: Date Range of Records, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
are_older_data_available_outsid (type: esriFieldTypeString, alias: Are older data available outside of that data management system?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes], [no: No])
what_formats_are_legacy_data_cu (type: esriFieldTypeString, alias: What format(s) are legacy data currently in?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
is_data_collection_conducted_au (type: esriFieldTypeString, alias: Is data collection conducted automatically or manually?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [automatic: Automatic], [manual: Manual])
how_frequently_are_new_observat (type: esriFieldTypeString, alias: How frequently are new observations received by your data management system?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
do_the_data_span_more_than_one_ (type: esriFieldTypeString, alias: Do the data span more than one table?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes], [no: No])
how_are_these_tables_separated_ (type: esriFieldTypeString, alias: How are these tables separated from one another?, SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
field_19 (type: esriFieldTypeString, alias: Is this data currently being shared publicly?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes], [no: No])
what_formats_is_this_dataset_pu (type: esriFieldTypeString, alias: What format(s) is this dataset published in?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
how_frequently_is_published_dat (type: esriFieldTypeString, alias: How frequently is published dataset updated?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
when_was_this_dataset_last_publ (type: esriFieldTypeDate, alias: When was this dataset last published?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
if_published_online_please_prov (type: esriFieldTypeString, alias: If published online, please provide a link to the data, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
could_this_data_be_modified_or_ (type: esriFieldTypeString, alias: Could this data be modified or aggregated so that it could be shared?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes], [no: No])
what_are_the_specific_restricti (type: esriFieldTypeString, alias: What are the specific restrictions on publishing this dataset?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
is_this_dataset_currently_machi (type: esriFieldTypeString, alias: Is this dataset currently machine-readable?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes], [no: No])
is_this_dataset_currently_human (type: esriFieldTypeString, alias: Is this dataset currently human-readable?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes], [no: No])
are_there_any_known_inconsisten (type: esriFieldTypeString, alias: Are there any known inconsistencies or inaccuracies in the dataset?, SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
how_much_subject_area_expertise (type: esriFieldTypeString, alias: How much subject-area expertise is necessary to understand the data?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [none_the_data_can_be_understood: None: the data can be understood by a beginner to the subject], [some_a_data_user_must_have_some: Some: a data user must have some familiarity with the subject to use], [extensive_a_data_user_should_ha: Extensive: a data user should have a deep understanding of the subject to use])